@bettina Having exposed pins/pads available directly on PyGo would allow to use PyGo as a platform for wearables which could be extended via different peripheral and interfaces - e.g. NFC, barcode reader, etc. The cradle is not a solution for these use-cases. Another approach might be to offer "OEM" PyGo which could interface with custom PCB designed by developer. It could be just the PyGo PCB or a PCB with one side of housing (with touchscreen display). The other side would be designed by developer depending on custom circuits/PCB. I am looking forward for F01 to be released. Is it going to use the same pinout of current OEM modules? What about module size? Is it going to be bigger? I would be grateful for more details as we are currently developing new product which might significantly benefit from F01.

Hi @co_buckfast, You could do this with Pygo (the actual device from Pylife system). If you struct.pack you data as timestamp, latitude, longitude 4B each * 3 = 12Bytes per record; there are 4MB available for user. So @30 sec update rate (I guess it's enough), 2 hours are 120 data records, so just 2.9 KB. This could also be quickly prototyped with any Wipy/Lopy/Fipy + Pytrack, battery and IP67 case. Downloading the data could be done over FTP/Wifi.